home *** CD-ROM | disk | FTP | other *** search
- Path: fido.asd.sgi.com!austern
- From: solution@gate.net (Ken Walter)
- Newsgroups: comp.std.c++
- Subject: Re: #ifdef XXXX
- Date: 06 Feb 1996 14:01:06 PST
- Organization: Solution Technology
- Approved: austern@isolde.mti.sgi.com
- Message-ID: <4f8edi$1jja@news.gate.net>
- References: <3112531A.3410@ElSegundoCA.ATTGIS.COM>
- NNTP-Posting-Host: isolde.mti.sgi.com
- X-Original-Date: 6 Feb 1996 20:41:22 GMT
- X-Newsreader: NeoLogic News for OS/2 [version: 4.2]
- X-Auth: PGPMoose V1.1 PGP comp.std.c++
- iQBVAwUBMRfPr0y4NqrwXLNJAQH0+AH+MPk5INH1djyuhAKPmX+w4sgNB1lKipqT
- HQDB5i0N48KhhmPloJsm/1UB8WaYJv7S+3V7QhMIZ/n7+zOcChClzQ==
- =5aYm
- Originator: austern@isolde.mti.sgi.com
-
- In message <DMBrxn.GAB@falcon.daytonoh.attgis.com> - Dick Menninger <Dick.Menni
- nger@daytonoh.attgis.com> writes:
- :>
- [...]
- :>>name techniques are needed to do other semantics. But an
- :>include file can be a form of template for source construction
- :>that could be included many times on purpose. That is what
- :>you are proposing to eliminate.
- [...]
-
- I don't see it eliminating old operation just adding a feature which is used
- frequently and is time consuming.
- The author of an included file knows if including beyond a point produces
- anything that is redundant and can tell the compiler to stop looking at it.
-
- I would even go farther and propose something like:
-
- #invariant
-
- which would tell the compiler to stop scanning this file if it already had
- scanned it before. This is not as efficient as not including it at all, but
- then the programmer doesn't need to know if the results are different each
- time.
-
- Ken Walter
-
- * All the above is hearsay and the opinion of nobody in particular
- ---
- [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu.
- Contact address: std-c++-request@ncar.ucar.edu. The moderation policy is
- in http://reality.sgi.com/employees/austern_mti/std-c++/policy.html. ]
-